Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1502

reference: 728-tree-1
name: 1502
tree-preservation-order: undefined
728-tpo-1
uprn
address-text
point: POINT (-0.988242 50.859783)
geometry: MULTIPOLYGON (((-0.988185 50.859777,-0.988187 50.859788,-0.988195 50.859798,-0.988208 50.859806,-0.988223 50.859812,-0.988241 50.859813,-0.988259 50.859812,-0.988275 50.859807,-0.988287 50.859799,-0.988296 50.859789,-0.988299 50.859778,-0.988296 50.859767,-0.988288 50.859757,-0.988276 50.859749,-0.988260 50.859743,-0.988243 50.859742,-0.988225 50.859743,-0.988209 50.859748,-0.988196 50.859756,-0.988188 50.859766,-0.988185 50.859777)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL